Fix the order of steps in the J2EE Installation document It is better to first define the JNDI data source in the application server and then deploy Gerrit than opposite. This should avoid errors like "No DataSource" on the first deployment. Change-Id: I89a2d1ab11bf0f7a44ee62f6d9083ab83bdd25a6 Signed-off-by: Sasa Zivkov <sasa.zivkov@sap.com>
diff --git a/Documentation/install-j2ee.txt b/Documentation/install-j2ee.txt index 96814a0..e6b748c 100644 --- a/Documentation/install-j2ee.txt +++ b/Documentation/install-j2ee.txt
@@ -27,12 +27,6 @@ review_site/bin/gerrit.sh stop ---- -* Deploy the 'gerrit.war' file to your application server. -+ -The deployment process differs between servers, but typically this -can be accomplished by copying 'gerrit.war' into the 'webapps/' -subdirectory of the container's installation. - * Configure JNDI DataSource 'jdbc/ReviewDb'. + This DataSource must point to the database you created above. @@ -40,6 +34,12 @@ necessary JDBC drivers. You may wish to ensure connection pooling is configured and enabled within the DataSource. +* Deploy the 'gerrit.war' file to your application server. ++ +The deployment process differs between servers, but typically this +can be accomplished by copying 'gerrit.war' into the 'webapps/' +subdirectory of the container's installation. + * ('Optional') Install Bouncy Castle Crypto API + If you enabled Bouncy Castle Crypto during 'init', copy the JAR 